Characteristics of Isolated License Managers

This section lists the characteristics of isolated License Managers:

Customized License Managers

The isolated License Managers are to be created by vendors by performing customizations in the software vendor specific isolated License Manager library. The 32-bit static library (lservnt.lib on Windows and liblserv.a on UNIX and Linux ARM.) is available at the following locations:

>On Windows: <installdir>\Development\C\Lib\x86\Static\IsolatedServer

>On UNIX: <installdir>/development/c/lib/x86/isolatedServer

>On Linux ARM: <installdir>/development/c/lib/<arm32hf/arm32sf>/isolatedServer

The customization workflow for isolated License Managers is described here:

NOTE   This library is different from the generic License Manager customization library installed at the following path:

>On Windows: <installdir>\Development\C\Lib\x86\Static\MT

>On UNIX: <installdir>/development/c/lib/x86/static

>On Linux ARM: <installdir>/development/c/lib/<arm32hf/arm32sf>/static
So, if you intend to implement isolated License Managers, you must use the isolated server library.

Using a communication port other than 5093

By default, the License Manager uses the reserved port 5093 for communication with clients. Therefore an isolated License Manager must use any other suitable port.

On the License Manager end, this can be set using the following alternative methods:

>As the software vendor – You can change the port by using the VLSchangePortNumber API function, provided in the License Manager customization library.

>As the system administrator – The system administrator can set the LSPORT environment variable or the -port start-up option.

Correspondingly, in the licensed application, the software vendor needs to call the VLSsetServerPort API function from the licensing library and specify the port number. You can also use the SNTL_ATTR_APPCONTEXT_SERVER_PORT attribute of the sntl_licensing_app_context_new Unified API for changing the port number.

NOTE   For information about modifying the TFTP port, refer to Redundancy and Isolated License Managers.

Loading Vendor-specific Licenses

An isolated License Manager will not load licenses belonging to other vendors (i.e. licenses generated using License Generators from other vendors).

Single License Manager Instance per System

Running multiple copies of the same isolated License Manager on the same host is prevented, even if they are using different ports.

The diagram below illustrates an updated customer site deployment scenario that now makes use of the isolated License Managers:

Figure 1: Sentinel RMS Isolated License Manager Usage Scenario

Now, system administrators can easily maintain separate licenses and other files to simplify auditing and troubleshooting activities. Switching to an isolated License Manager may also result in improved performance as a smaller number of licenses are loaded onto each License Manager concurrently.